Research
Security News
Kill Switch Hidden in npm Packages Typosquatting Chalk and Chokidar
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
graphql-config-parser
Advanced tools
The easiest way to configure your development environment with your GraphQL schema (supported by most tools, editors & IDEs)
The easiest way to configure your development environment with your GraphQL schema (supported by most tools, editors & IDEs)
TLDR: Set an environment variable called GRAPHQL_ENDPOINT
to your GraphQL endpoint (e.g. https://your.api/graphql
) or read ahead for other configuration options.
Relay.QL
queriesDid we forget a tool/editor? Please add it here.
You can either configure your GraphQL endpoint via a configuration file or by providing an environment variable.
Note: This requires Node 5 installed or higher
$GRAPHQL_ENDPOINT
environment variableThe easiest way to configure your project is by setting an environment variable called GRAPHQL_ENDPOINT
to your GraphQL endpoint.
export GRAPHQL_ENDPOINT="https://your.api/graphql"
.graphqlrc
fileYou can either use your actual GraphQL endpoint or if preferred a local schema.json or schema.js file.
Note: The headers
object is optional and can for example be used to authenticate to your GraphQL endpoint.
{
"request": {
"url": "https://example.com/graphql",
"headers": {
"Authorization": "xxxxx"
}
}
}
{
"file": "./schema.json"
}
{
"graphql-js": "./schema.js"
}
package.json
fileUse the same configuration options as for the .graphqlrc
file but wrap it into an object with the key graphql
.
{
"dependencies": { ... },
"graphql": {
"request": {
"url": "https://example.com/graphql"
}
}
}
This project aims to be provide a unifying configuration file format to configure your GraphQL schema in your development environment.
Additional to the format specification, it provides the graphql-config-parser
library, which is used by all supported tools and editor plugins. The library reads your provided configuration and passes the actual GraphQL schema along to the tool which called it.
In case you provided a URL to your GraphQL endpoint, the graphql-config-parser
library will run an introspection query against your endpoint in order to fetch your schema.
graphql-config-parser
API import { parse, resolveSchema } from 'graphql-config-parser'
const config = parse()
resolveSchema(config)
.then((schema) => {
// use json schema for your tool/plugin
})
.catch((err) => {
console.error(err)
})
Join our Slack community if you run into issues or have questions. We love talking to you!
FAQs
The easiest way to configure your development environment with your GraphQL schema (supported by most tools, editors & IDEs)
The npm package graphql-config-parser receives a total of 67 weekly downloads. As such, graphql-config-parser popularity was classified as not popular.
We found that graphql-config-parser demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.